Support for Access Keys

The accesskey attribute assigns a particular key on the phone to an element. Its purpose is to allow the user to activate a particular element using a single key. For the Web browser, an access key is a single Dialpad button and the element is a URL. The access keys associated with the IP telephone Web browser are as follows:

In Table 11 each of the Dialpad button access keys is mapped to a different URL. For example, when the “2” button on the dialpad is pressed, the example2.com URL is launched because it is mapped to the “2ABC” button, as shown in the following code example:

<a href="http://example2.com/contents/wml" accesskey="2">
 

Similarly, to inform the Web server that any of the Keypad buttons were pressed, the Table 11 example URLs would be launched for any of the 12-keypad buttons. Each button is assigned to a different access key and URL. Each button to be tracked must have a URL mapped to it in the page. If the page author wants to know whether any of the 12 possible Dialpad buttons are pressed, then the page must include access keys pointing to specific URLs.

Button presses do not distinguish among the characters a button represents. For example, if a user presses Dialpad button 2, it is impossible to distinguish anything other than the user pressed the second button. No refinement is made to inform the Web server that the user meant 2 or A or B or C.

An AIM application is one where the page currently being loaded contains <a> or <anchor> tags with access keys defined. The application developer has a choice of mapping every keypad entry to a URL or can opt to leave some unmapped keypad entries. The <a> or <anchor> tags support the accesskey attribute. The correct syntax is:

NOTE: The <input> tag does not support the accesskey attribute because AIM and standard Text Entry cannot be mixed on one page.